A Single Suite can be a member of one Linked Suite only.
Only Single Suites can be members of Linked Suites.
Only the Hospitality Gateway ICP in a clustered hospitality environment can host Linked Suites. The suites can reside on any element in the cluster if Shared Telephone Service (STS) is disabled for the Linked Suite in the Linked Suites form. Otherwise, the suites must also reside on the gateway.
Suite members in a clustered hospitality environment must be hosted by the same Hospitality ICP as the suite pilot.
Check in, check out, and move room operations apply to the Suite Pilot number only.
Linked Suite and Member Suite Pilot Numbers include a maximum of seven digits when managed by PMS.
Names, locations, and department information are managed from either guest services or the PMS system.
Comments for room specific information may be programmed in the Comments field on the Suites form (not in the Telephone Directory form).
All suite members follow the Class of Service and Class of Restriction of the first member programmed in the suite (Primary Suite Extension). For example, if Conference Call is set to No for the Primary Suite Extension, none of the suite members can use the Conference Call feature.
If all Members of a Linked Suite are in Do Not Disturb mode, then all calls follow call rerouting configured for the Primary Member Suite.
Maid status can be changed at any room telephone and is applied to the Suite Pilot number.
Outgoing calls will follow the suite, not the linked suite, behavior.
All calls made to and from a Member Suite include the Linked Suite Pilot number (recorded in SMDR).
Non-Busy Extensions (NBEs) are not supported.
Suite Services affects the following user interfaces:
CLASS Phone Redial List, which clears when the guest checks out. Suite Extensions that receive CLASS information provide a clear command.
Class of Service, which can be used to limit programming of Superkey call forwarding (Linked Suites only).
Guest Services, where suites and rooms are both presented as Rooms
Hotel logs, where suites and rooms are both presented as Rooms.
You cannot assign Suites, Linked Suites, and Guest Room devices with local-only directory numbers. You must assign them with cluster-dialable directory numbers.
There are two methods to provide Suite functionality. One method, using the Suites form, requires that each member be licensed individually. The other method, using the Multi-device Suites form, requires just one license for the entire suite.
Depending which method you select, different license and service level settings are required. These differences are illustrated in the following table.
|
Suites configuration |
Multi-device Suites configuration |
License Settings |
Each suite member consumes IP User licenses (and possibly an EHDU license) when the member is programmed on the Suites form. The suite does not consume a license. |
The suite consumes a Suites license when it is programmed on the Multi-device Suites form. The members do not consume licenses. |
Service Level Settings |
Each suite member, including the Primary Suite Extension, must be programmed as a Full Service or Trusted Service user. |
All suite members, including the Primary Suite Extension, must be programmed as Multi-Device users. |
NOTE: Multi-device suites have slightly reduced functionality compared to regular suites. For example, when one member of a Multi-device suite is engaged in a call, the other members are restricted to IP Device Only behavior. Refer to Multi-device Suite Conditions for a complete list of limitations.